﻿<Page x:Class="TreeBuilder.Help.GeneralInfoPage"
      xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
      xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
      xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" 
      xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
      xmlns:m="clr-namespace:TreeBuilder.Help" xmlns:Controls="clr-namespace:Elderos.Controls;assembly=Elderos.Controls" mc:Ignorable="d" 
      d:DesignHeight="300" d:DesignWidth="640"
	Title="General info">
    <Page.Resources>
        <ResourceDictionary Source="pack://application:,,,/Help/HelpStyles.xaml"/>
    </Page.Resources>
    <Controls:HelpMasterPage>
        <Controls:HelpMasterPage.Title>General info</Controls:HelpMasterPage.Title>
        <Controls:HelpMasterPage.Content>
            <Grid>
                <RichTextBox BorderThickness="0">
                    <FlowDocument>
                        <Paragraph Style="{StaticResource HeaderStyle}" Margin="10,0,10,0">
                            Why do you need it?
                        </Paragraph>
                        <Paragraph Margin="0">
                            TreeBuilder is a (linguistic) syntax tree editor. It's the easiest way to build syntax trees I know.
	                        You can create a tree, save it to a picture file or save it to a reopenable *.tree format
                            and edit it later. The picture can be easily integrated to any editor (such as MS Word).
	                        Alternatively, you can print a big poster, hang it on the wall and enjoy the beautiful view.
                        </Paragraph>
                        <Paragraph Style="{StaticResource HeaderStyle}" Margin="10,0,10,0">
                            Why did I make it?
                        </Paragraph>
                        <Paragraph Margin="0">
                            When I created TreeBuilder, my main goal was to provide an easy way to build (linguistic)
                            syntax trees. All methods I've seen before are far from perfect. The main problem
                            is the specific appearance of syntax trees: they have had a standard form for
                            a long time, namely, each node has no borders, all nodes are aligned by their inheritance
                            level etc. I've seen people using graph editing programs, MS Word drawing features,
                            *TeX and even special font, but none of this ways is acceptable. The trees built
                            in these ways are hard to edit, hard to use and hard to support.
                        </Paragraph>
                        <Paragraph Style="{StaticResource HeaderStyle}" Margin="10,0,10,0">
                            Some history
                        </Paragraph>
                        <Paragraph Margin="0">
                            This is already the 3rd version of program. It became a bit more usable and received
	                        MS Word-like interface. The first two versions were built on .NET WinForms technology,
	                        which could offer neither high performance, nor great interface possibilities. I
	                        tried to make people use the previous version, but only few of them really used
	                        it. I think the reason was the poor usability, poor appearance, poor help file and
	                        some bugs. That's why I decided to create a completely new application on a new
	                        WPF platform. I hope this program will help you.
                        </Paragraph>
                    </FlowDocument>
                </RichTextBox>
            </Grid>
        </Controls:HelpMasterPage.Content>
    </Controls:HelpMasterPage>
</Page>
